Jira is a Saviour
Jira Software is a project management tool that is widely used by various teams in our organization to manage their projects and tasks. …
Starting at $81.85 per month 10 users
View PricingOverview
What is Jira Software?
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Standard
$8.15
Cloud
per month per user (minimum 10)
Premium
$16
Cloud
per month per user (minimum 10)
Data Center
$44,000
On Premise
per year 500 users
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://www.atlassian.com/software/jira…
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $81.85 per month 10 users
Product Demos
JIRA Project Management Tutorial for Beginners (2022)
YouTube
The full overview: Roadmaps in Jira Software
YouTube
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is Jira Software?
Jira Software is a project management tool software used by agile teams and supports any agile methodology, be it scrum, kanban, or a team's own unique flavor. From agile boards to reports, users can plan, track, and manage agile software development projects. And since not every team works the same way, Jira Software allows teams to customize workflows, permissions, and schemes to match the unique needs of each team.
Jira templates also support use cases in enterprise marketing management, and projects to support operations, design HR, and enterprise marketing management.
With Jira Software, teams are able to:
- Track versions, features, and progress at a glance
- Re-prioritize user stories and bugs
- Estimate stories, adjust sprint scope, check velocity, and re-prioritize issues
- Estimate, track and report on story points; become more accurate
- Report on agile metrics to provide real-time, actionable data on team efficiency, quality, and overall performance
- Integrate with all the tools their dev team is already using, from the rest of the Atlassian suite (Bitbucket, Bamboo, Fisheye, and Crucible) to other popular developer tools on-premise or cloud (e.g., GitHub and Jenkins).
- Provide greater flexibility to curate which teams have access to which information with sprint and project-level permissions
- Flexibly tailor Jira tasks and their workflows to a specific team's use case
- Extend Jira with over 1,800 apps from the Atlassian Marketplace to fit any capability not provided by default
Jira Software Videos
Jira in a Nutshell Demo Video
Jira Software is a software development project management tool of sorts, that tracks progress, offers up project reports, and gives a great roadmap view to understand workloads and deadlines better. In this video, the TrustRadius team goes over Jira Software pricing, top feat...
Show More Jira Software Integrations
Jira Software Competitors
Jira Software Technical Details
| Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Windows, Mac |
| Mobile Application | Apple iOS, Android |
Frequently Asked Questions
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Jira Software starts at $81.85.
Reviewers rate Support Rating highest, with a score of 8.8.
The most common users of Jira Software are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(3244)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Pros
- Cons
Easy-to-use tool with minimal learning curve: Users have found JIRA to be an intuitive and user-friendly tool that requires minimal effort to learn. Several reviewers mentioned that they were able to navigate through the platform easily and quickly adapt to its features.
Seamless collaboration through integration with other tools: Many users appreciated JIRA's ability to integrate with various plugins and add-ons, enabling seamless collaboration across different teams and departments. This integration allowed for enhanced productivity by bringing together different tools into one centralized platform.
Flexibility of customization: The flexibility of JIRA in terms of customization was highly regarded by users. They mentioned being able to customize bugs, tasks, and stories based on the specific requirements of their projects. This flexibility helped them tailor JIRA to their unique project management needs.
Confusing and overwhelming user interface: Many users have expressed frustration with the confusing and overwhelming user interface of JIRA. They find it difficult to efficiently complete tasks due to a lack of intuitive navigation and cluttered design.
Complexity and difficulty in customization: A significant number of reviewers find JIRA's customization options to be complex and challenging. It often requires dedicated training to effectively navigate and utilize the software's customization features.
Limitations in reports, charts, and attachments: Users have reported challenges in sharing information within JIRA due to limitations in reports, charts, and attachments. These limitations hinder effective collaboration, communication, and data visualization.
Attribute Ratings
Reviews
(1-24 of 24)Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
My organization uses JIRA to organize projects and track velocity across teams. The business problem that this product addresses for my company is that we use it as a tool to communicate asynchronously across large project teams, report our tracking metrics, project-manage, and even plan and develop larger product roadmaps.
- Organization - JIRA is great for being able to organize the scope of major features or product launches in a way that can be visualized across teams.
- Communication - In a remote-first world, JIRA allows you to maintain tight communication and aligned scope even as teams work across time zones.
- Velocity Tracking/Project planning - JIRA allows teams to visualize and understand expectations for when to deliver a project, have insight into project/team/individual capacity, and track work overtime.
- Learning curve - There is a learning curve to working in JIRA, it is not immediately intuitive to a new user. It usually requires a lot of learning in order to most effectively and optimally use JIRA. A lot of it comes with time and experience.
- Lack of standardization - There are a lot of bells and whistles in JIRA. It's really great that you can label or organize tickets in a variety of different ways. It is really up to the organization to create a method of organizing within all of those bells and whistles. This means each time you go to a new organization, there is a lot of overlap, but you are learning a lot of new methods and best practices as well.
- JIRA can be a little bit frustrating and hard to use in terms of the ability to type and format content in each epic or individual story. It's good enough and JIRA has done a lot recently to add integrations (such as Figma) or other ways to link design, but it can be sometimes hard to translate complex requirements into JIRA in a consumable way.
October 06, 2023
Extremely good on workflow monitoring and handy reporting tools
JIRA is being used by multiple departments within IT group. We used it mainly for bug and defect tracking, we also use it to coordinate and communicate tasks within a single or multiple department. It solves the hassle of tracking and documenting our activities and it also enables us to summarize progress and generate reports easily.
- JIRA does particularly well on tasks and activities tracking.
- It allows users to easily incorporate supporting documents with various formats.
- Easy monitoring and summarizing and is also flexible on assigning and commenting on a task.
- Sometimes the software is unresponsive
- I also experiencing some bug occasionally
- Comments are viewed and order historically, hence it's difficult to have context if commenting on older comments
Score 8 out of 10
Vetted Review
Verified User
We mainly use Jira software for tracking issues, tasks & bugs.
- Problems addressed by this software:
1. Keeping the whole team in single and transparent track.
2. Helps in solving issues more efficiently.
3. Bugs tracking is more effective.
- Scope of use case:
1. It is very important tool in terms of software development lifecycle.
2. Helps in tracking bugs and overall enhancing the security features of our product.
3. It helps business in terms of reducing overall cost.
- Problems addressed by this software:
1. Keeping the whole team in single and transparent track.
2. Helps in solving issues more efficiently.
3. Bugs tracking is more effective.
- Scope of use case:
1. It is very important tool in terms of software development lifecycle.
2. Helps in tracking bugs and overall enhancing the security features of our product.
3. It helps business in terms of reducing overall cost.
- Effective work visualization using Kanban board feature.
- Work-in-progress limit is very helpful for increasing overall work efficiency.
- Bugs, issues & story creation very easy using this tool.
- Some tools and features are not very user-friendly at first.
- Sometimes difficult and complex to configure.
- We will recommend some efficient learning community to be made to address this.
The CS, Engineering, and Product teams use Jira Software to manage platform defects, feature requests, and tasks. We also use Jira Software to track projects for new apps and improving existing apps. This is a cornerstone application for us since it runs our entire Engineering and Product operations.
We rely on Jira Software to prioritize work across multiple groups inside the Engineering team who handle different aspects of the platform. Having cross-functional visibility is key to understand and track the workload being distributed across the backend and frontend teams.
We rely on Jira Software to prioritize work across multiple groups inside the Engineering team who handle different aspects of the platform. Having cross-functional visibility is key to understand and track the workload being distributed across the backend and frontend teams.
- Customizability is impressive. Being able to establish automations and custom fields of all types helps when we need to build new templates to support different efforts.
- Integration into third-party apps like Git, Bitbutcket, and Zendesk helps streamline our processes and visibility across teams.
- Easily customizable dashboards are a huge help when it comes to analyzing the vast amount of data available in Jira Software.
- Bloated - the app has so [many] features and functionality that it tends to bog down from time to time.
- Expensive - Jira Software is by far one of the most expensive offerings out there.
- No dark mode support - it's 2021, we should have [a] dark mode.
- Nickle and dime features - Need to pay for common functionality like Git integration.
- Lack of automated alerts around metrics like ticket age, last update, etc.
April 14, 2022
Better tracking, traceability, agile view dashboards...
Score 9 out of 10
Vetted Review
Verified User
Good issue tracking tool with all features defined clearly. Also, helps us manage daily agile activities with better viewability. But, can be improved in some areas. Examples: UI is too subtle, search patterns are not good enough, etc. The tool helps in tracking all items individually or separately using dashboards. Helps user manage their work and see live progress within the team.
- Tracking Progress
- Agile
- Dashboard
- Issue Management
- Search Patterns for GRID data does not work.
- UI is too subtle and hence less interesting.
- Finding access groups for particular dashboard URLs is difficult.
The entire organization uses Jira Software, although to varying levels and in different ways. On my individual team we use it more to plan for upcoming projects and track tasks or bugs. It allows us to not only assign out responsibilities and see their status, but also to determine their priority and also estimate the amount of impact and time the task will take.
- Offers a variety of ways to create dashboards to view projects, boards, tickets, etc based on any number of personal preferences
- Can easily receive notifications regarding a project's progress when the ticket is updated by being a watcher on the ticket
- Offers a robust number of settings for a project board's tickets and how they can be created
- Is best suited for concrete, clear tasks to be assigned and doesn't work as well for more abstract, loosely defined projects
- To create projects with multiple steps, the use of Epics can become clunky and integrating dependencies into the process is not easily done
- It's not terribly intuitive and a new user of Jira Software likely will have a steep learning curve
July 07, 2021
A reliable issue tracking system for an agile team
<div>We use Jira to track every single task that all engineering teams execute. Either for unexpected tasks or for planned tasks that follow the product roadmap, we use Jira to track every task/story that the agile teams work on every spring and daily.</div><div><br></div><div>We also use Jira to quantify each team's capacity, see the progress and evolution of our products, and see how close we are following the schedule to complete the roadmap of each project.</div>
- Team collaboration
- Task management
- Third party integration
- Documentation
- Estimation
- Jira on premise allows to easily make mistakes avoidable with Jira on cloud
- Jira on cloud is faster to implement but restrictive compared to on premise
Jira Software is used across the firm to track and manage projects, [including] tasks. It addresses prioritizing projects, keeping track of all projects to be worked on, and in progress or completed for users, and developers. Jira allows the business to enter new requirements and tasks; [also assigns] them to developers and prioritize them. Jira helps managers to fix bugs quickly; [also] to track and document [any] bug fix. It also helps identify potential issues by creating a place holder for issues that require additional research, so that the issue is not forgotten. Jira allows [for] effective reporting of issues based on a particular criteria which is important for weekly status meetings.
- Allows quick and efficient way to enter a project, task or issue to be further researched and then tracked until completion.
- Does a great job of managing and tracking issues, as well as all the important attributes for each project or issue.
- Has a very good search and reporting mechanism.
- Makes tracking projects or simple tasks easy. [It has] good customization and the data is informative.
- Integrates well with other software tools, including but not limited to: FishEye + Crucible, Wiki, and TeamForge.
- Does not integrate with CM tool, such as SVN, which would be useful for managing software releases.
- Search features are difficult to use and to import results for reporting. There is some learning curve on these features since it is using programming language.
- The Kanban board on Jira [has bugs] and often produces error alerts, even though changing a status still works.
- For certain projects in the software , it is less intuitive to close an item. For instance, sometimes you have to move the item back to TO DO status in order to close it out.
May 13, 2021
Jira - the software project management king
Jira is an integral part of our organization. If it's not used across the whole organization it's probably close to 90%. We use it to manage our internal software projects and products. We also have clients that use Jira Software where we are asked to create and manage tickets. It helps keep us organized and accountable for our work and efforts on any project.
- Organize
- Customization
- Accountability
- Steep learning curve
- No dark mode
- Legacy Jira was arguably better
April 29, 2021
For Agile, Jira is the best
We use Jira Software at IT Development and IT Operations processes. Approximately 500+ users use Jira Software. Jira Software provides major contribution to our Agile Software Development process with flexible, easy to use and collaboration features. We use Jira Software for managing development squad kanban boards, making performance reports, sprint planning, [and] sprint retrospective reviews.
- Easy to create board and dashboards
- Flexible
- Customizable
- Has a learning curve, but not very much
- Need some plugins like big picture, confluence etc
- First setup
August 14, 2019
JIRA works
JIRA Software is used by the website development group. It tracks our new projects, our system bugs, and system problems. We use it to communicate with our workers who are off-site. We also use JIRA with Github to number our Git branches. Using JIRA's ticket codes keeps everything in sync and reduces problems.
- Project tracking
- Individual task tracking
- Integration with Github
- Communication with team members is adequate but not as good as other software
- Not as many software integrations as I would like
- Can't delete tasks unless you are super user
We use JIRA as a project management and a bug tracking tool for most of the company projects. Whether it is software development, ASIC design or IP development, JIRA fits all flavors. For software development, we use it mainly for its agile scrum and Kanban development support. We realized that switching to Agile with JIRA was a winning combination to increase productivity, together with having more homogeneous teams and same mindset across team members.
- Easy to use bug tracking features.
- It has a great support for Agile SCRUM and Kanban software development methodologies.
- Promotes collaboration within the team and across teams.
- It is extremely configurable and allows a system admin to address complex project management requirements.
- There is a steep learning curve for JIRA administrators before the full potential of the tool can be harnessed.
- The licensing system is per number of users. If you buy a small license and the tool is widely adopted, you may have an issue in getting your budget approved in a low cost environment, because the price for higher tiers goes up quickly.
- Support can use some improvement. It happened few times that for critical issues we had to spend a lot of time exchanging emails and explaining to different people where the problem was.
August 09, 2019
JIRA - Managing a Project Activity at your Fingertips!
Score 10 out of 10
Vetted Review
Verified User
JIRA is used by our Company to setup Epics and the associated Tasks that belong with the Epic. We then plan our Sprint (2 weeks) with Development tasks and track the progress of those tasks. If something happens that hinders the development of such task, we can easily put a block on that Task until the block can be removed (i.e. waiting on data cut from Agency). We can easily drop something into the backlog when needed.
- Manages Epics (projects) very well. Tasks can be adjusted easily along with their corresponding Story Points. The Backlog can be easily managed by moving Tasks around as needed.
- Notifications can be automatically sent out (if setup) to the Developer when new work is assigned.
- Epics/Tasks/backlog items can be managed through an easy to use drag and drop process.
- Agile. Easy to work with (very intuitive)
- I don't have anything negative to say about the software.
- As with any software, the GUI can always use improvement, but that comes with time.
- It can lock up very briefly at times due to too many users.
Score 8 out of 10
Vetted Review
Verified User
We're using Jira as a tool to be in control of our projects. We use it for tasks and much more. We use it across all of our organization and highly appreciate the options of integrating Jira with Bitbucket. It's important to stay agile and Jira does the job. We can use the software between departments - design, development, etc. Our project managers have the option to get a better idea of what we're doing and how much time we're using during the tasks.
- Tasks
- Project management
- Agile boards
- Ticketing for problems etc.
- Complex user management.
- User management can be to complex for non-trained users.
- Very expensive.
- Could services sometimes crash?
April 25, 2018
Solid Organizational Tool
JIRA software is currently being used within our department as an organizational tool. JIRA is being used intermittently across the whole organization, but is not currently a standard. JIRA really helped our team with organization and collaboration as it breaks down work and assignments in a simple and visible way.
- Easy and efficient way to organize and assign work
- Allows for the creation of a hierarchy of tickets and work to keep priorities organized
- User-friendly and cost efficient as an organizational tool
- Training resources readily available
- Being able to create epics would be highly useful for better organization and maintenance
- Being able to split the work, or tickets, between team members would also be useful
- There is a learning curve which does require time and resources to adapt to the tool
February 27, 2018
Jira- Effective Tool to manage Agile Teams
It is being used at a program level in the organisation. We use JIRA to track our Agile teams that are [composed] of Scrum and Kanban teams. We use it for tracking epics, stories, issues, tasks, subtasks, production maintenance tracking, and planning.
It provides a good dashboard where higher leadership can look at how things are progressing and ultimately bringing in transparency.
It eliminates the need for individual teams to send weekly or monthly status reports to leadership on progress and what they are involved with. So at team level sprints, stories, epics, sizing, capacity, scrum and Kanban boards are managed and looked at.
- Requirements are managed very well there which can be captured in the form of epics.
- Epics, which capture the high-level ideas can be broken down into stories, tasks and sub-tasks.
- The team can team can raise bugs, capture comments and tag test cases, against each story ultimately bringing end-to-end traceability.
- Since distributed agile requires more collaboration, JIRA's seamless integration with communication tools like HipChat and Slack allows teams to work collaboratively.
- JIRA supports customization since each team is unique, you can create your own issue types, modify the workflows, add/remove fields.
- Standard issue types created in any project are: a) Bug b) Task c) Sub-Task d) Epic e) Support Ticket f) User story
- User Story workflow can be: a) Backlog b) Ready to Start c) Dev In-Progress d) QA In-Progress e) Ready for Demo All these can be modified based on your requirements.
- If you are looking for devops implementation, JIRA has support for CI & CD.
- It can be integrated with Git and Jenkins very well.
- JIRA supports two kinds of boards, Kanban and Scrum boards. It is very easy to track things using these boards & it also provides ample of charts like reporting options such as burndown charts to help teams plan & replan at every stage in the development life cycle
- Searching issues in JIRA is very simple through JQL (Jira Query Language).
- If we would like to perform a complex search JQL allows to find issues from any timeline.
- The basic version of Jira do not have support for test management, capacity management & release management.
- So users have to buy various plugins to support these basic functionalities which can prove costly based on team size.
- Navigation around the UI can be difficult at times
- Jira is not a simple tool, it requires some training before users can start working on it so some learning curve is involved.
March 20, 2017
Very few issues with managing issues
JIRA is used by R&D in order to work on adding features and improvements, as well as identifying and repairing bugs. JIRA is also used by engineering for working on server and data center issues. Lastly, JIRA is used by application support at a tier 2 and tier 3 level for troubleshooting single user issues.
- Creating dashboards for issue tracking and management.
- Highly customizable and many plugins are available.
- Logging, tracking and updating issues via email.
- Useful for project management but not flexible enough to effectively use for other purposes.
- The search function is poor.
- Interface is not terribly user-friendly.
November 03, 2016
Jira: Swiss Army Knife of Agile Sprint tools.
We are using Jira across our agile office's sprint teams. Jira provides a collaboration model and workflow for developers, QA testers, and architects. Jira addresses our business's need for transparency: supporting the SCRUM framework of time-boxed sprint deliveries and supporting the IT department's production releases.
- Jira provides ease of use issue entry and workflow to developers, testers and architects. The Plan view works great for estimating and grooming sessions. The Work board allows full collaboration for the team's Stand Ups.
- Jira's sprint report area offers a daily view of burndown chart, sprint report, epic report, etc.
- Jira's filters and gadgets in the non-agile build are built-in. I use them every morning to create a daily dashboard. The Pie charts gadgets of Status and Assignee are clickable to the pie wedge, moving you right to the story or bug. Very cool!
- Jira could provide a Favorites list of recently used gadget/filter combinations when creating a new dashboard.
- Jira could provide a url link to Atlassian forums or Jira blogs that updates when opening the application.
- Jira could provide a history drop in the quick search field of the Plan view to help find that hidden story or bug quickly.
August 02, 2016
JIRA - The Godzilla of bug tracking softwares
JIRA is the main bug-tracking/requirement software used by my company. QA uses it to document bugs and keep track of the progress of a project. They also use it to report results to persons outside the team by using issue tracking Dashboards. Developers use it to set tasks for themselves and monitor their progress. Product uses it to set up Requirement tickets and define scope of project.
- The software is user friendly and there is almost no learning curve with this.
- The software is ubiquitous enough where most people that are hired have already used it before and so there is not much need for extensive training on it.
- There is enough flexibility while writing an issue to customize the bugs/tasks/stories based on the type of project it belongs to.
- There are a lot of ways to effectively track issues using different labels/customized fields etc.
- It is easy to set up a workflow in a project.
- The advanced search option is extremely helpful and flexible.
- The permissions for users are pretty hard to navigate through. The permissions controls are not user friendly and easy to understand or implement.
- There need to be more gadgets added to the Dashboard feature to make it more diverse and useful. Especially a text gadget should be a default option available and not an add on.
- There is no way to effectively sort tickets linked to one ticket.
April 27, 2016
JIRA, at the forefront of the industry.
We use JIRA in conjunction with our partner. During our prototype design phase we use it to track any issues encountered by either party. It is also used during a products life cycle should any problems be found by customers or if redesigns are necessary. JIRA is used exclusively by one department in our company. It addresses the need for transparency and communication between the necessary developers.
- Issue tracking.
- Project management.
- Variable workflows.
- High learning curve.
- Not viable for certain types of development.
- "Clunky" user interface.
April 18, 2016
Quick Atlassian JIRA review
JIRA Software is used for tracking bugs, enhancement requests, and development of tasks/sub tasks.
- Ability to set customized processes/workflows.
- Ability to integrate other tools, such as Testrails and Jenkins, and send notifications via email or IM programs.
- Still learning about JIRA and have not found any big holes or missing functionality.
April 08, 2015
Atlassian JIRA has significantly improved our work intake and request tracking processes
Our organization uses JIRA for work intake and tracking across multiple departments. It was initially implemented by our Software Development department to manage day-to-day support requests and bug fixes. However, it was so successful that nearly every other department has set up their own project(s) and developed new processes for managing their work intake, centered around JIRA. When used in conjunction with JIRA Agile (it used to be called GreenHopper), JIRA is a fantastic tool for identifying bottlenecks in the process. We use it for work intake, prioritization, tracking, and ultimately as a record of work completion.
- Excellent for use as a repository for work requests
- Allows easy prioritization of work requests
- Can be highly customized to match your processes
- The administrator tools can be difficult to understand - there is a pretty steep learning curve if you want to start customizing
- I wish you could attach a screenshot during issue creation - I don't know why it's available once the issue is created, but not as part of creation
We're using JIRA across the organization to build digital products in Agile with onshore and offshore development teams.
- Planning board allows good visibility into sprints as well as backlog, making it easy to organize and prioritize
- Integration with Confluence allows easy cross-referencing between Product Requirements and User Stories
- Integration with HipChat allows for asynchronous communications across time zones.
- Information Architecture between JIRA and Confluence is abysmal, can be difficult to navigate between the two
- OnDemand instance has limited add-ons.
- HipChat would greatly benefit from a shortcut that links issue numbers directly to tickets
December 18, 2014
A skeptical JIRA user won over
JIRA was our ticketing system and Project Management tracking tool. We used JIRA both for incident management and enhancement/deployment tracking. We also used JIRA to pull statistics to determine how quickly dev teams were turning requests around and how quickly support teams were reacting to cases, updating them, and ultimately resolving them. I mostly used JIRA's reporting features to determine where bottlenecks were in our reporting and development structures.
- JIRA is extremely customizable, especially when compared to Atlassian's other flagship product, Confluence. We were able to tailor a JIRA process flow for every development and support flow that we had, even before JIRA.
- JIRA reports well. While we did find some holes in what we were able to report on, 90% of what we needed was there and readily accessible once a user was familiar with the reporting structure.
- JIRA interacts fairly well with other products. We were able to integrate it into Confluence (as it should be), but we were also able to build plug-ins into Outlook, Excel, and our phone system for more advanced functionality.
- JIRA is far too cumbersome. The learning curve to become proficient was sharp enough to cause several of our less technical people to give up learning how to truly utilize the tool, and keep things very basic. It ended up being handed over to Engineering (me, in particular because of my success with Confluence), and I also found it cumbersome but not really difficult to learn.
- While not an issue for us, I can see potential for a business to need to tailor their process around JIRA and how JIRA perceives typical ticketing/PM process.
- There are quirks with how JIRA chooses to think of business process that make the creation of some work flows more difficult and the path to engineer them less than intuitive.